Part of #38

SO WE HAVE:

• STREAMING FROM ELASTICFEED TO THE JS-CLIENT
• POSSIBILITY TO TRIGGER EVENT ON CHANNEL LEVEL, FEED LEVEL, ENTRY LEVEL

TO DO: see related feedlabs/sdk-js#10

• SEND REQUESTS FROM JS-CLIENT TO ELASTICFEED
  • ACTION: MORE DATA, INIT DATA ETC.
  • VIEWER ABSTRACTION ON UI END <-> PERSON ON SERVER SIDE (POPULATION MEMBER)
  • METRICS:
    • SAVE ENTRY: ACTIONS, HABITS, BEHAVIOURS ETC
• SERVICES
  • API STORAGE END-POINT
  • STREAM BI-POINT
  • METRICS END-POINT
  • PREDICTION END-POINT
  • PVP END-POINT (PRIVATE VIRTUAL PERSONALITY)
• SERVICE MANAGER
  • SKELETON
• POPULATION MANGER
  • SKELETON
  • HUMAN
  • SOCIETY
  • PRIVATE VIRTUAL PERSONALITY (PVP)
• PVP CONTROLLER
  • SKELETON
• HUMAN CONTROLLER
  • SKELETON
• PLUGIN MANGER
  • SKELETON
  • RESOURCE API
• WORKFLOW MANAGER
  • SKELETON
  • HOOKS
  • EVENTS
  • FLOWS
    • PRE-LEARNING
    • DISTRIBUTION
    • LEARNING
• WORKFLOW CONTROLLER
  • SKELETON
  • INITIALIZATION
  • VIEWER CONTEXT
  • INTERNAL API
  • PLUGIN MANAGMENET
  • EXECUTE PLUGIN CHAINS
  • ARTIFACTS
• STATE ENGINE (CLUSTERING)
  • LIST OF FEEDs with binded SOCKETs (optimization); cluster ready
• AUTHENTICATION
  • FOR FEED ACCESS